Fixes an issue where var keywords were not being correctly tokenized in tuple deconstruction patterns at the top level (outside of methods), causing them to appear as regular variables instead of type keywords.

Problem

When using tuple deconstruction with var keywords at the top level:

(int _, var _) = (1, 2);
(var _, var _, var _) = ('a', 'b', 'c');

The var keywords were being tokenized as variable.other.readwrite.cs (regular variables) instead of storage.type.var.cs (type keyword), preventing them from being highlighted correctly in the editor.

Root Cause

The local-tuple-var-deconstruction pattern only matched var (x, y) = ... syntax but not (var x, var y) = ... syntax at the statement level. When at the top level, the parenthesized expression pattern would match first and treat var as an identifier.

Solution

Added a new local-tuple-declaration-deconstruction pattern to the grammar that:

• Matches tuple deconstruction with type/var declarations: (type/var id, type/var id) = ...
• Uses tuple-declaration-deconstruction-element-list to properly handle var keywords
• Is included in local-declaration so it's checked before general expression patterns

Changes

• Grammar fix: Added local-tuple-declaration-deconstruction pattern in src/csharp.tmLanguage.yml
• Test coverage: Added 4 test cases covering both Input.InMethod and Input.FromText scenarios for:
  • Mixed type and var: (int _, var _) = (1, 2);
  • Multiple vars with discards: (var _, var _, var _) = ('a', 'b', 'c');

All 897 tests pass. The var keyword is now correctly tokenized as storage.type.var.cs at both method and top levels.

• Fixes var in tuple deconstruction #316

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.